The One Question You Keep Not Asking Your Team

There's a thing on your team nobody says out loud anymore.

Maybe it's the handoff between design and delivery that fails every second sprint.

Maybe it's the person whose drafts always come back needing a rebuild.

Maybe it's the client who rings one of your people directly and skips the whole intake process.

Whatever it is, your team has built a workaround for it. The workaround has been running so long it looks like the process.

And somewhere between the office and your driveway, you've asked yourself a question you've never said to another human being: why can't I just name it?

You've drafted the sentence. You've got as far as opening your mouth in a one-to-one. Then you heard how it sounded, and you asked about the roadmap.

The answer nobody gives you

The advice you'll get is about courage. Be brave. Have the hard conversation. Address it head on.

That advice assumes the thing in short supply is nerve. It usually isn't in short supply. You've told a client no. You've delivered bad news about budgets. You've sat in a room and fired someone.

What actually stops you is the wording. Every draft in your head has a subject, a verb, and a defendant. You can't find a version that doesn't land as an accusation, so you wait for a better sentence to arrive. It doesn't arrive. The workaround gets another month of practice.

This should worry you. The people who work for you are running the identical loop. When Frances Milliken and two colleagues at NYU Stern interviewed 40 employees, 85 percent said they'd been in a situation where they felt unable to raise something to a supervisor even though they believed it mattered. Among those who felt uncomfortable speaking up, 74 percent said colleagues who knew about the same issue felt uncomfortable too.

So the thing you're not naming, they're not naming either. Each of you reads the other's silence as a settled decision.

What Rina found in the tracker

Rina runs a nine-person operations team at a freight forwarding firm. In her second week, a new coordinator called Dev asked her a question nobody else had asked in five months: why does every job in the tracker have two dates on it?

Because documents sent to Faisal, the senior reviewer, came back roughly two days late. Every time. So since March, the team had been entering a private internal deadline two days ahead of the real one and treating the second date as the one that counted.

Nobody had told Faisal. Faisal thought he was hitting his dates, because from where he sat, he was.

When Rina finally asked him about it, the cause took ninety seconds to surface. In February he'd been added to a second team's review queue as a favor. Nobody told him that the queue was optional. He'd been treating neither as mandatory and was quietly falling behind on Rina's.

Five months of a workaround that required one conversation to solve. The fix was an email removing him from a queue he never wanted.

That's the ordinary shape of these things. The unnamed problem almost always has a boring cause, and the boring cause is almost always fixable in a week. What kept it alive was that naming it felt like an accusation, and nobody could find the wording.

The harder version of the question

Stop asking why you can't say it.

Ask this: what would I have to say for the other person to stay in the room?

That question has answers. There's real work on which words trigger a defense and which ones open a door.

​Kristi Hedges, a Washington DC executive coach and author, told a group of investors at a leadership conference that asking someone "why" creates the expectation of a full explanation and can be heard as "questioning their intelligence, their integrity." Her suggestion is to keep the curiosity and drop the word: ask what led to something or how the person saw it at the time.

The vague version fails for a different reason. Claire Lew, a chief executive who writes about managing teams, argues that "How can I help you?" hands the employee the delicate work of diagnosing you and hands it to them without warning across a power gap. You already know how that lands. You've asked "Everything okay?" in a one-to-one, gotten "Yeah, all good," and gone back to the roadmap, feeling like you'd checked a box.

The sentence, in three parts

Write yours down before Monday. Three parts, in this order.

• One: the observation, with a number or a date in it and no adjective anywhere. "We've been running two dates on every job since March," not "There's been some friction around reviews." A specific detail is hard to argue with and impossible to take as a character judgment.
• Two: your own share, said before theirs. "I set that review step up in January, and I haven't looked at it since." This costs you almost nothing and changes the whole arithmetic of the conversation for the person listening.
• Three: an open question starting with what or how. "What would make that step work for you?"

Then stop talking. Count to ten in your head. The first silence after part three is where the actual answer lives, and it belongs to them.

The part that matters most

Going first is the whole mechanism. The person across from you is running a fast, mostly unconscious calculation about what happens to them if they're honest. Naming your own contribution before you name theirs is the only move in the sequence that changes the answer to that calculation, and it takes about eleven seconds.

You'll be tempted to skip it. Part one feels like the brave bit, and part three feels like the generous bit, so part two reads as filler. It's the load-bearing one.

Rina's tracker has one date on it now. Dev has stopped asking.